-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Put shards failure under a cap flag #131371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Pinging @elastic/es-analytical-engine (Team:Analytics) |
Since the new behavior in serverless, which does not have CCS, perfectly matches the behavior of the search API, do we still want to disable it in serverless? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @smalyshev !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. We might need to adjust some tests as they can fail in the release builds. Thanks Stas!
Oops noticed the |
💔 Backport failed
You can use sqren/backport to manually backport by running |
* Put shards failure under a cap flag (cherry picked from commit 0411940) # Conflicts: # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/action/EsqlCapabilities.java
* Put shards failure under a cap flag (cherry picked from commit 0411940) # Conflicts: # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/action/EsqlCapabilities.java
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
This reverts commit 0411940.
No description provided.